Restful Service Composition

The Service-Oriented Architecture (soa) has become one of the most popular approaches to building large-scale network applications. The web service technologies are de facto the default implementation for soa. Simple Object Access Protocol (soap) is the key and fundamental technology of web services. Service composition is a way to deliver complex services based on existing partner services. Service orchestration with the support of Web Services Business Process Execution Language (wsbpel) is the dominant approach of web service composition. Wsbpel-based service orchestration inherited the issue of interoperability from soap, and it was furthermore challenged for performance, scalability, reliability and modifiability. I present an architectural approach for service composition in this thesis to address these challenges. An architectural solution is so generic that it can be applied to a large spectrum of problems. I name the architectural style RESTful Service Composition (rsc), because many of its elements and constraints are derived from Representational State Transfer (rest). Rest is an architectural style developed to describe the architectural style of the Web. The Web has demonstrated outstanding interoperability, performance, scalability, reliability and modifiability. Rsc is designed for service composition on the Internet. The rsc style is composed on specific element types, including restful service composition client, restful partner proxy, composite resource, resource client, functional computation and relaying service. A service composition is partitioned into stages; each stage is represented as a computation that has a uniform identifier and a set of uniform access methods; and the transitions between stages are driven by computational batons. Rsc is supplemented by a programming model that emphasizes on-demand function, map-reduce and continuation passing. An rsc-style composition does not depend on either a central conductor service or a common choreography specification, which makes it different from service orchestration or service choreography. Four scenarios are used to evaluate the performance, scalability, reliability and modifiability improvement of the rsc approach compared to orchestration. An rsc-style solution and an orchestration solution are compared side by side in every scenario. The first sce-